-
Notifications
You must be signed in to change notification settings - Fork 972
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
misc(share/p2p): reduce frequency of discovery retries #3561
base: main
Are you sure you want to change the base?
Conversation
… modify in test environments in a sane way
if p.AdvertiseRetryTimeout <= 0 { | ||
return fmt.Errorf("discovery: advertise retry timeout cannot be zero or negative") | ||
} | ||
|
||
if p.DiscoveryRetryTimeout <= 0 { | ||
return fmt.Errorf("discovery: discovery retry timeout cannot be zero or negative") | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't this config breaking? If so, let's mark PR as such.
… away if accidentally mistaken for a bees nest
There is some wisdom behind the metaphor in ca67fef, but I am not getting it |
@Wondertan ah, I put it back how it was, so no unnecessary change :-) |
Let's hold off on this til we get conf from v0.14.1 |
Fixes #3550 as suggested by guillaumemichel. In adjusting the "1 liner" realized there was some relatively funky stuff in tests where we set/reset a package level var for the interval, so moved both AdvertiserRetryTimeout and DiscoveryRetryTimeout to parameters and allowed customization where NewDiscovery is called. Also adjusted some of the intervals to be faster in tests so they execute within the test context Timeout and thus, hopefully will fix #3115